Pull requests must include at least one of the required labels: internal, highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

PR Summary

This PR improves the documentation workflow for the template schema by introducing two major enhancements:

1. A dedicated documentation section has been added to the README that provides instructions on regenerating the auto-generated documentation. It explains how to run the scripts (such as generate_permissions_docs.py and generate_template_schema_docs.py) along with their dependencies (e.g. Python 3.9+ and required packages). This aims to keep the documentation in sync with backend changes.

2. A new Python script (scripts/generate_template_schema_docs.py) has been introduced. This script leverages the json-schema-for-humans package to generate HTML documentation from the backend JSON Schema. It also performs post-processing on the generated HTML by:

   • Injecting custom CSS overrides for Quarto compatibility
   • Prepending a copyright header
   • Replacing parts of the theme to include a Quarto stylesheet
   • Cleaning up temporary files after generating the final output file

Additionally, the template documentation file (site/guide/templates/customize-document-templates.qmd) has been updated to reference the auto-generated HTML file instead of embedding a large chunk of static HTML inline. This separation helps with maintainability and ensures that changes to the backend schema are automatically reflected in the documentation.

Overall, the changes streamline the process of updating documentation by automating the extraction and formatting of backend JSON Schemas into readable site documentation.

Test Suggestions

• Run the 'generate_template_schema_docs.py' script in an environment where the backend repo is cloned at the expected relative path (../backend) and verify that the output file is correctly generated under 'site/guide/templates/_template-schema-generated.html'.
• Modify the backend JSON Schema (e.g. mdd_template_schema_v5.json) and re-run the script to ensure that changes are accurately propagated to the generated documentation.
• Test the inclusion of the generated schema file in 'customize-document-templates.qmd' to verify that the documentation renders correctly on the site.
• Simulate missing dependencies (e.g., uninstall 'json-schema-for-humans') to ensure that the script fails gracefully with an appropriate error message.